Repository navigation
Keep the run log on newly started simulations - #137
Merged
Merged
Conversation
rhorvath02
force-pushed
the
fix/follow-new-simulation-log
branch
from
October 19, 2026 09:43
98832f0 to
2c24a6f
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Keep the run log on the simulation that just started. Refresh the job list before opening the log so its render cannot replace the new selection with an older job. Clear the previous log and reset its scroll position.
Stacked on #136.
How to check
node tests/app_editor_clarity.cjspasses, including a regression that renders the log immediately when it opens while an older job exists.